fix: allow any JSON Schema type for outputSchema #1169
+6
−17
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
commit: |
The MCP spec does not require outputSchema to have type: 'object' at the root level - it can be any valid JSON Schema. This allows tools to return arrays, primitives, or other structures for list/batch responses. inputSchema still correctly requires type: 'object' since tool inputs are always named parameters. Fixes #1149
domdomegg
force-pushed
the
adamj/fix-output-schema-restriction
branch
from
3e41a67 to
b567184
Compare
Contributor
|
MCP spec does require outputSchema to have type: 'object' at the root level - see https://modelcontextprotocol.io/specification/draft/schema#tool. Relaxing this restriction has been proposed, but it remains in the present spec unless I've missed a late-breaking development. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The MCP spec does not require
outputSchemato havetype: 'object'at the root level - it can be any valid JSON Schema. This allows tools to return arrays, primitives, or other structures for list/batch responses.inputSchemastill correctly requirestype: 'object'since tool inputs are always named parameters.Fixes #1149